Remote control brake system and manifold

ABSTRACT

A locomotive brake system includes a plurality of electronic air brake controllers for controlling at least a train brake pipe and a locomotive brake pipe interconnected by a communication network. A communication port and a system controller are connected to the network. The system controller controls the configuration of the electronic air brake controllers for standard mode and remote mode of the brake system and assembling EAB network signals for communication between a remote locomotive controller to be connected to the communication port and the electronic air brake controllers.

CROSS REFERENCE

The present application is a continuation of U.S. patent applicationSer. No. 11/531,891 filed Sep. 14, 2006 and which is incorporated hereinby reference.

BACKGROUND AND SUMMARY OF THE INVENTION

The present invention relates generally to locomotive brake systems andremote controlled locomotives (RCL) and more specifically to adaptationof a locomotive brake systems as a remote controlled locomotive (RCL).

One remote controlled locomotive or remote operated locomotive systemusually includes a remote control transmitter (RCT) carried by anoperator. In the industry, these are known as belt packs. Alternatively,there may be a console in the yard or a tower. The RCL systems are usedto move a locomotive and the cars over a very short distance at a verylow speed. It usually allows a remote operator not on the train tooperate the system. The RCL systems control the propulsion and brakingof the locomotives.

Another form of remote control of locomotives is communicating from alead locomotive to remote trailing locomotives distributed throughoutthe train. The operator at the control of the lead mode locomotive setsthe propulsion and braking at the lead locomotive, and appropriatesignals are sent to the remote locomotives that are in trail mode toexecute the required braking or propulsion. This may be the same brakingor propulsion setting, or it may be a customized setting depending uponthe location of the remote locomotive within the train. In this group ofcontrol over remote locomotives, the actual primary locomotive brakesystem is that which is being controlled. It controls not only the brakeof the locomotive but may also operate on the brake pipe, which runsthroughout the train.

Historically, RCL systems have used a standalone control of thepropulsion and brakes on the train. This is in parallel to the standardlocomotive control system. It has been suggested that the system used tocontrol remote locomotives may also be adapted to use the primary brakesystem to be responsive to a portable remote control transmitter or beltpack. This requires appropriate interlocks and safety measures since itoperates with the primary braking system. Such a system is shown in U.S.Pat. No. 6,964,456, which is incorporated herein by reference.

Present intelligent Electronic Air Brake (EAB) Systems developed forrailroad locomotives are designed to interface with other subsystems asdistributed power (DP) and electronically controlled pneumatic (ECP)train brakes. Such a system is shown in U.S. Pat. No. 6,334,654, whichis incorporated herein by reference. An example is the CCB II systemavailable from New York Air Brake. These integrations are subsystemspecific as they are designed, and software written, that operateexclusive for that subsystem. Intelligent components of one EAB cannotbe interchanged with that of another subsystem without compromising thefunctionality. This also is true with subsystems of like functionalitybut of differing OEM suppliers.

Remote Controlled Locomotive (RCL) subsystems available from differentOEMs are of varying structures, interfaces and degrees of operability.Each OEM has their unique braking interface, be it pneumatically‘serial’ or ‘parallel’ of the locomotive's braking system. Eitherconfiguration is reliant on the locomotive's core braking system.Typically, the RCL subsystem is the control of each power and brakingfor a railway vehicle, such as a locomotive. The RCL comprises on-boardequipment that has a direct interface to the Electronic Air Brake (EAB)equipment as well as the power equipment and various feedback devicesthat are not within the confines of the EAB equipment. The on-board RCLsubsystem may receive Operator commands remotely through an RFinterface, tether cord and/or wayside equipment. The RCL may becompletely without a human operator as commands are generated bydistributed intelligence.

It is desirable to provide an EAB system which interfaces with diverseRCL subsystems, while maintain interchangeability of EAB core componentsand keeping a high degree of safety. Preferably this is achieved byappropriate connection of the devices without reprogramming the softwarein the system.

The present locomotive brake system includes a plurality of electronicair brake controllers for controlling at least a train brake pipe and alocomotive brake pipe interconnected by a communication network. Acommunication port and a system controller are connected to the network.The system controller controls the configuration of the electronic airbrake controllers for standard mode and remote mode of the brake systemand assembling EAB network signals for communication between a remotelocomotive controller to be connected to the communication port and theelectronic air brake controllers.

The system may include an interface device connected to thecommunication port and configured to interface the EAB network signalsand signals of a remote locomotive controller connected to the interfacedevice. The interface device may include a plurality of RCL ports forconnection to a remote locomotive controller and interfaces the EABnetwork signals at the communication port and the signals at the RCLports. The plurality of interface devices communicate with each other onthe network by RCL signals and each has an RCL port for connection to aremote locomotive controller. One of the interface devices is a primarydevice which interfaces the EAB network signals of the communicationport and the RCL signals of the interface devices. The interface devicemay be configured to interface the EAB network signals and serialdigital signals, parallel digital signals or analog signals of a remotelocomotive controller connected to the interface device.

The system controller assembles train and locomotive brake signalsreceived from the communication port and transmits to the electronic airbrake controllers, and assembles and transmits status signals to thecommunication port. The controller may poll the communication port todetermine the type of remote locomotive controller is connected to thecommunication port and assembles EAB network signals for communicationbetween a remote locomotive controller to be connected to thecommunication port and the electronic air brake controllers for thedetermined type of remote locomotive controller.

The system controller initially may poll all the electronic air brakecontrollers and assign an identifier to each which authorizes them tohave a remote mode. Upon replacement of one of the electronic air brakecontrollers, the system controller or one of the authorized electronicair brake controllers assigns an identifier to the replacement whichauthorizes it to have a remote mode.

The brake system may include a cut-in system connected to the trainbrake pipe and the locomotive brake pipe to provide a braking signals onthe train brake pipe and the locomotive brake pipe when the cut-insystem is initially activated and subsequently controlled by the systemcontroller to provide releasing signals on the train brake pipe and alocomotive brake pipe once the brake system is in the remote mode. Thecut-in system may include a pressure sensor monitoring the brake signalprovided to the locomotive brake pipe and providing an activation signalto the system controller. The system controller monitors conditions ofthe locomotive brake system during receipt of the activation signalbefore setting the remote mode and to maintain the remote mode.

These and other aspects of the present invention will become apparentfrom the following detailed description of the invention, whenconsidered in conjunction with accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic of a prior art electric air brake system havingelectric air brake controllers connected by a network.

FIG. 2 is a signal flow diagram of an electric air brake systemincorporating remote control capability according to the presentdisclosure.

FIG. 3 is a signal flow diagram for a remote control locomotiveequipment having three discrete interface devices.

FIG. 4 is a signal flow diagram for a remote control locomotive with aserial to LON connection.

FIG. 5 is a flow schematic of an auxiliary application unit according tothe present disclosure.

FIG. 6 is a logic diagram for entering and exit the remote controllocomotive mode.

FIGS. 7 and 8 are diagrams illustrating remote mode authorization ofreplaced electronic air brake controllers.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 show a known Electronic Air Brake (EAB) subsystem 10 consists of‘intelligent controllers’ that are linked and share information orcommands over an EAB network 12. As an example, a CCB II available fromNew York Air Brake and shown in U.S. Pat. No. 6,036,284 is incorporatedherein by reference. There are five intelligent controllers depicted inFIG. 1 as depicting a typical railway locomotive arrangement. Thequantity and functional characteristics of intelligent controllers mayand do vary between braking subsystem applications.

An operator inputs manual control commands for braking of a railwayvehicle through the Operators Command Controller 14. The operator'scommands are then communicated to the appropriate intelligent controllerfor the movement of compressed air to the application or release ofbraking effort. For example, an Equalization Reservoir Controller 16responds to commands from the EAB network 12 in response to operatorinput of the Operators Command Controller 14 to electronically control apressure level in an equalization reservoir. A Brake Pipe Controller 18is responsive to signals on the EAB network 12 and the value of thepressure in the equalization reservoir to control the pressure in thetrain brake pipe. The Equalization Reservoir Controller 16 and the BrakePipe Controller 18 make available the pressure level status of theequalization reservoir and the train brake pipe respectively over theEAB network 12, to all the intelligent controllers.

An Independent Braking Controller 20 responds to commands on the EABnetwork 12 from the Operators Command Controller 14 to electronicallycontrol a pressure level in a trainline or locomotive brake pipe(commonly referred as Independent Application & Release Pipe). TheIndependent Braking Controller 20 makes available the pressure levelstatus of the locomotive pipe, over the EAB network 12, to all theintelligent controllers.

The EAB network 12 is the means of the EAB subsystem 10 to relay brakingcommands and status throughout the subsystem of intelligent controllersto provide operation of the railway vehicle's brakes. Also on the EABnetwork 12 is a Vehicle Input/Output Interface Controller 22 and aCommunication Node 24. The Communication Node 24 may be part of or inthe Vehicle Input/Output Interface Controller 22. Other locomotivesystems are connected to the EAB via the Vehicle Input/Output InterfaceController 22, such as Distributed Power, Electronically ControlledPneumatic brakes, etc.

Additional intelligent controllers are added to the EAB network 12 forthe option of allowing input commands of braking from a RemoteControlled Locomotive (RCL)' subsystem 30 in lieu of that of theOperators Command Controller 14 as shown in FIG. 2. The vehicleinput/output interface controller 22 has been shown as a system controlnode. It may also be known as a Relay Control Portion (RCP) in anelectronic air brake system now known as CCB 26 system available fromNew York Air Brake Corporation. A description of the CCB 26 may be foundin the article, “The CCB 26 Locomotive Brake System 26 L Replacement forthe Next Generation,” by John M. Reynolds, published in the Proceedingsof the 97^(th) Annual Conventional and Technical Conference in theAmerican Brake Association of Sep. 19-20, 2005, pp 127-140. Such asystem is described in a paper. The Communication Node 24 is shown asperipheral node 24.

Peripheral node 24 is on the EAB network 12 and is shown as providingLON command messages and heartbeat 26 to the system control node 22 viathe EAB network 12. System control node 22 provides LON status messageand heartbeat 28 to the peripheral node 24 over the EAB network 12.Please note that this is a signal flow diagram and not a mechanicalconnection since they are interconnected and communicating to each otherover the EAB network 12. The peripheral node 24 communicates andprovides interface to the RCL equipment 30 via connection 32 andprovides command and status by a discrete or serial connection. Thisconnection is a function of the structure and the interface requirementsof the RCL equipment 30.

The system control node 22 receives a discrete RCL activate input signal27. This is independent of the EAB network 12. It may also provide aseries of discrete outputs on terminal 29.

The RCL subsystem 30, as well as DP, ECP or any interface wanting thecontrol of train or unit brakes, have two fundamental or primary needsfrom the EAB subsystem 10. Namely control of the brake pipe through theequalizing reservoir pressure, and control of the locomotive's brakethrough the independent application & release pipe as well as theactuating pipe (bail).

At the minimum, the core braking logic needs to respond to enforcementbraking overriding that of the RCL. Emergency reductions have priorityas break-in-two, Operator or Fireman. Safety equipment penalties,pneumatically activated on the EAB system are honored.

Part of the fundamental needs is communication of status information tosignal the proper response of train brake and locomotive braking to theRCL subsystem 30. At the minimum this would include brake pipe andindependent pipe pressures. It is the diversity between RCL of thevarious status or feedback signals required from the EAB subsystem toeach unique control scheme(s) that defines their equipment.

The present system is designed to provide a wide diversity of interfacesand allow flexibility in OEM required functionality or uniqueness, whilemaintaining its' core interchangeability. In doing so, there are ‘RCLfoundation design rules’ within the core EAB logic to ensure componentinterchangeability. If/When this foundation rules are compromised, thenRCL subsystem interchangeability of EAB core components are compromised.

The system controller 22 controls the configuration of the electronicair brake controllers for standard mode and remote mode of the brakesystem and assembling EAB network signals for communication between aremote locomotive controller to be connected to the communication port24 or the interface nodes 24 and the electronic air brake controllers.The interface nodes 24 are configured to interface the EAB networksignals and signals of a remote locomotive controller 30. The interfacenodes 24 may include a plurality of RCL ports for connection to a remotelocomotive controller 30 and interfaces the EAB network signals and thesignals at the RCL ports. The plurality of interface nodes communicatewith each other on the network by RCL signals and each has an RCL portfor connection to a remote locomotive controller 30. One of theinterface nodes 24 is a primary device which interfaces the EAB networksignals of the communication port and the RCL signals of the interfacedevices, as shown in FIG. 3. The interface node 24 may be configured tointerface the EAB network signals and serial digital signals, paralleldigital signals or analog signals of a remote locomotive controllerconnected to the interface device.

The system controller 22 assembles train and locomotive brake signalsreceived from the RCL system 30 via the interface nodes 24 and transmitsto the electronic air brake controllers, and assembles and transmitsstatus signals to the interface node 24. No special re-programming ofthe system controller 22 is required for the different systemrequirements of the different RCL equipment 30. Variations inconnectivity is provided by the interface nodes 24 which are RCLspecific.

An RCL subsystem 30 interface to EAB system 10 would either be Discreteor Serial. Discrete is that of a combination of digital and analogsignals as that of today's pneumatic interfaces. Serial is that ofcommand and status passed through a communications protocol.

The RCL subsystem interface is input/output through intelligent controlNode(s) 24 that are placed onto the core EAB network 12. The Node(s) 24are OEM interface specific. The Node(s) 24 are the gateway into the coreEAB braking logic. The EAB braking logic, or core control portions(nodes), has the functional remote logic. The Node(s) 24 handle thespecific interface requirements be it multiple discrete or serial(optional communication).

A single RCL Command and a single RCL Status message protocol for theEAB network is defined for operation of EAB system to encompass all theforeseeable variable factors allowed under RCL control. These distinctRCL Messages are the functional interface messages within the core EABbraking logic. The system control or Relay Control Portion's (RCP) node22 logic is the ‘pilot’ between the RCL subsystem 30 and the EAB brakinglogic. The RCP 22 receives the RCL Command Message, disseminates anddelivers to the appropriate EAB controllers. The RCP 22 also collectsthe defined status data from the EAB controllers to build and send theRCL Status Message.

The defined response to RCL command and feedback of status is universalfor the EAB braking logic. Responses are defined for all thoseconfigurations and/or options foreseen. These are the RCL foundationdesign rules.

Translation and content of these messages are performed by the RCLperipheral node(s) 24. Those commands that are not directly receivedfrom the RCL subsystem 30, commands that are optional in nature, are‘default’ set commands by a peripheral node 24. Those statuses that arenot required by the particular RCL subsystem 30 interfaced are simplynot translated by the peripheral RCL node 24.

Whereas there is more than one interface node 24 to the RCL subsystem, aprimary node is designated as the pilot of these peripheral nodes.Referring to FIG. 3; Architecture for example, the node 24A isdesignated the primary. The 24A node receives the RCL Status Message,disseminates and delivers to the appropriate 24B, 24C or more node(s).The 24A node also collects the defined command data from the 24B and/ormore nodes 24 to build and send the RCL Command Message.

As shown in FIG. 3, the interface node 24 includes three intelligentcontrollers or interface devices 24A, 24B and 24C. The interface devicescontroller 24 include an input 32 for an analog command signal from theRCL 30 and an output 38 of an analog status signal to the EAB status tothe RCL 30.

Interface devices 24B and 24C provide command signals to the primaryinterface device 24A over the EAB network 12 as illustrated by lines 34Band 34C respectfully. The status signals from the primary interfacedevice 24A are provided to interface devices 24B and 24C over the EABnetwork 12 as illustrated by lines 36B and 36C. The primary interfacedevice 24A communicates LON command messages by line 26 to the RCP 22 asillustrated and receives LON status via line 28 from RCP 22.

One example for the configuration of FIG. 3, is that the primaryinterface node 24A would receive the train brake command while interfacedevice 24B would receive the locomotive brake command. The appropriatestatus of these brake applied can then be transmitted back through 24Aand 24B. The interface 24C may provide other status informationrequested, for example, air flow measured by the EAB system 10.

A serial to LON interface node 24 is illustrated in FIG. 4. The RCLsystem 30 provides commands over serial port 32 and receives status viaport 38. The interface node 24 provides the commands to the RCP 22, overthe network 12 as illustrated by lines 26 and receives the statussignals back from RCP 22 via over the network 12 as illustrated in lines28.

The number of interface devices is not fixed and nor are means ofsharing the commands of status as analog signals. Although FIGS. 3 and 4shows the software interconnection of these modules, they may bephysically connected in series on a single comport 24 depending upon theEAB system 10. For example, they may be connected in series with theoperation command controller EBV to the port for the EBV on the EABsystem 10.

The interface devices may be serial communications of RS-232 or 422 toLON, digital input/output through EAB control nodes as well as theanalog input/output device. Communication interface could be Ethernet ordirect MIP. Interfaces may be singular or of any combination.

The actions to be taken on system failures or fault detections by thebraking system of an RCL equipped locomotive are different than that ofmain line or conventional EAB operation. Thereby, the design of an EABfor dual purpose operation, either RCL or Conventional, need be equippedfor differentiating fault actions. An Auxiliary Application Unit (AAU)is provided to overlay the RCL enforcement braking requirement onto theconventional EAB operation.

The AAU 40, as shown in FIG. 5, has a ‘manual’ Cut-In or Cut-Out deviceor double port cut-off DPCO 42 and 42A for an RCL enforcement brake. Itconsists of a normally de-energized magnet valve 44 for the initiationof emergency brake application via emergency application valve 11 of theEAB 10 and a normally de-energized magnet valve 46 for full applicationof independent braking. This unit has a sensor 49 that indicates to theEAB 10 as an RCL Activate signal, that the AAU 40 is Cut-In with airpressure for the required application of independent effective braking.The RCL subsystem 30, responsible for braking control, is in directcontrol of the emergency and independent magnet valves 44,46. Magnetvalves must be energized to release brakes. A pressure sensitive valve48 is also provided at the output the device 42A.

The Cut-In of the AAU 40 results in the application of braking on theunit irregardless of the power or mode state of the RCL subsystem 30.The EAB subsystem 10 can no longer operate in a Conventional mode. TheAAU sensor 49 is the RCL Activate input 27 (FIG. 2) to the EAB brakingsystem 10 via the system control node RCP 22 as conventional operationis no longer desired due to the potential hazards associated with RCL'senforcement brake. A double check valve 13 in the EAB 10 applies thelarge of the independent or locomotive brake signals from the EAB 10 andthe AAU 40 to the IA&R locomotive brake pipe.

Normally, the EAB system 10 is in the standard EAB mode and responsiveto the signals from the operator's command controller 14 and the DPCO 42is in Cut-out. To enter RCL operation or RCL Mode, a defined Set-Up isrequired. As previously described, there are different enforced brakingrule sets when operating in RCL then when in Conventional or EAB Mode.Also, these rule sets are in force when the DPCO 42 of the AAU 40 ismanually opened. Thereby, the pressure switch PS-EN 49 of the AAU is theinput directly to EAB system 10 as a command to Activate RCL mode ofoperation.

Note that an emergency brake application shall occur and the independentbrake will fully apply on opening of the DPCO 42.

Assurance of the ‘rule set’ between operational modes is critical tosafe operation. The change to RCL operation of braking is not desiredunless braking is healthy, brakes are presently applied and commandstatus with the RCL subsystem is healthy.

Secondly, no response is taken directly to the RCL activate inputcommand when in conventional or EAB mode of operation. This avoids anundesired emergency brake application which is the detected faultresponse of EAB in RCL mode.

FIG. 6 describes the set-up conditions and required conditions totransfer states in response to the RCL Activate command or PS-EN of theAAU 40.

At Step 50 the DPCO 42 of the AAU 40 is manually set to the cut-in mode.Next it is determined at Step 52 whether this has occurred by measuringthe pressure on the locomotive brake pipe by sensor 49. If the pressuresensors switch 49 is closed, which indicates that the DCPO 42 is incut-in mode, it is next determined at Step 54 whether the EAB system 10is in the trail mode. If it is in the trail mode at Step 56, it isdetermined whether there is an EAB brake enforcement. If there is thenat Step 58, it determines whether the locomotive or unit brakes areapplied. If they are, it is determined at Step 60 whether the RCLcommand brakes are applied on the train brake pipe. If they are, the EABsystem 10 under the control of the system control node 22 sets the EABsystem 10 to the RCL enable mode. This directs each of the EABcontrollers to receive their controls from the RCL subsystem 30 insteadof the operator's command controller 14.

At Step 52 if the pressure sensor 49 is open meaning the pressure islow, it is determined at Step 64 whether the RCL is enabled, if it is,an emergency application is provided at 66 and the system is set totrail at Step 68. The RCL is disabled at Step 70 and the EAB system 10enters the EAB mode at Step 72.

Note that an exit from RCL mode of operation is immediate and distincton the loss of RCL Activate input through an emergency brake applicationinitiation by EAB 10. RCL 30 is not allowed to operate without the AAU40 being Cut In.

The RCL subsystem interface is optional to the EAB core or basesubsystem. There is then a license security algorithm within the EABsubsystem to allow individual EAB intelligent controllers to beinterchanged between non-equipped and that of differently equipped RCLsubsystem vehicles.

An RCL subsystem requires its' unique RCL intelligent interfacecontroller(s) within the EAB network 12 of the EAB subsystem 10. Onlythose railway vehicles supplied with an RCL subsystem would have an RCLprimary intelligent controller. The RCL primary intelligent controlleris the license controller which authorizes the EAB controllers to have aRCL or remote mode. In the previous figures, the license controller maybe the primary interface node 24 or the system control node 22. In theexamples of FIGS. 7 and 8 the license node will be signified by RCL A.

The RCL A is connected to a ‘non-licensed’ EAB subsystem 10. The RCL Ahas a license algorithm that is set to execute in its entirety a singletime. On prompt, as in a request to enter RCL operation, the RCL A willexecute this license algorithm. The RCL A shall poll the EAB network 10to create a ‘list’ of RCL interface devices and/or EAB Controllers(D-H). With all present and accounted, the RCL A shall then authorizeRCL mode of operation for each RCL Device (B-C) and/or EAB Controller(D-H). Each RCL Device (B-C) and/or EAB Controller (D-H) is thenlicensed and retains licensed RCL operation mode. The primary RCL DeviceA at completion of execution of its license algorithm does not execute asecond time. Only reset by the OEM will allow reset of licensealgorithm.

In the afore mentioned description, an EAB Controller D through H may beinterchanged between RCL equipped and non-equipped rail vehicles withoutbeing unique or otherwise having the same identifier. The EAB Controllerinterchanged may not be licensed for RCL operation. As described, an EABController will retain its' authorized RCL operational mode. Interchangeof an EAB Controller requires the removal of power of the EAB subsystem.On power-up, a non licensed EAB Controller, for example D, will poll theother EAB Controllers, for example E-H, and reliant on their licensestatus, and then authorize itself into the RCL operational mode.

Typical maintenance practices for a railway vehicle would require theremoval and interchange of several EAB Controllers at the same time. Theprimary RCL and two of the EAB Controllers, namely the Operator'sCommand Controller 14 and the Vehicle Input/Output Interface Controller22, are not typical interchanged in routine maintenance practice. Anycombination two of three of this configuration will authorizeinterchanged EAB Controllers.

An embellishment of the license disallows the inevitable cumulativecollection of authorized Controllers that makes up a newly licensed EABsubsystem. Referring to FIG. 7, those intelligent controllers identifiedwith a 1 are those that have been authorized by the license schemedescribed. For illustration, EAB G controller has recently beeninterchanged with that of a non authorized controller, designated with a(0). As described above, in an on power cycle, EAB G will become enabledto 1 as has EAB D that had previously been exchanged. There is nowavailable an EAB G-1 and an EAB D-1 that are authorized. Eventually,through exchange of controllers, there shall be an entire EAB subsystemthat shall be authorized. Eventually all controllers would becomeauthorized removing the optional criteria.

Means of prevention is to randomly reassign a subsystem number anytime acontroller is authorized. Controllers of a different number, outside thelicense scheme defined above, are non-authorized. Those of differentnumbers, but are within the confines of the license scheme, propagate asubsystem number reassignment. Referring to FIG. 8. EAB G controller hasrecently been interchanged with that of a non-authorized controller,designated with a (0). In the power cycle, EAB G will become authorized,however each designator within this subsystem shall be set to a randomnumber, different to either that already assigned (8). The designator(8) had been assigned on the interchange of EAB D-3 earlier. There isnow an EAB G-8 and an EAB D-3 that are authorized. As these controllerscarry differing designators, and to the rules of the license schemerequiring the correct or allowable combination of like designators toauthorize, the natural progression through exchange of controllers to acomplete enabled subsystem is very unlikely.

Although the present invention has been described and illustrated indetail, it is to be clearly understood that this is done by way ofillustration and example only and is not to be taken by way oflimitation. The scope of the present invention are to be limited only bythe terms of the appended claims.

1-18. (canceled)
 19. A locomotive brake system comprising: a pluralityof electronic air brake (EAB) controllers on a locomotive connected toand controlling at least a train brake pipe and a locomotive brake pipeand being interconnect by an EAB communications network; an interfacedevice on the locomotive and connected to the EAB communication networkand configured to interface with the EAB network signals and the signalsof the remote locomotive controller (RLC) to be connected to theinterface device on the locomotive; and a system controller on thelocomotive and connected to the network, the system controllercontrolling the configuration of the electronic air brake controllersfor an EAB mode and a remote mode of the brake system and assembling EABnetwork signals for communication between a remote locomotive controllerto be connected to the interface device on the locomotive and theelectronic air brake controllers, whereby the air brake controllerscontrol the brake pipes in response to signals from the remotelocomotive controller.
 20. The system of claim 19, wherein the interfacedevice includes a plurality of RCL ports for connection to a remotelocomotive controller and interfaces the EAB network signals and thesignals at the RCL ports.
 21. The system of claim 19, wherein theinterface device includes a plurality of interface devices connected toand communicating with each other on the network by RCL signals and eachhaving an RCL port for connection to a remote locomotive controller, andone of the interface device is a primary device which interfaces the EABnetwork signals and the RCL signals of the interface devices.
 22. Thesystem of claim 19, whereas the interface device is configured tointerface the EAB network signals and digital signals of a remotelocomotive controller connected to the interface device.
 23. The systemof claim 19, whereas the interface device is configured to interface theEAB network signals and analog signals of a remote locomotive controllerconnected to the interface device.
 24. The system of claim 19, whereasthe interface is configured to interface the EAB network signals and acommunication protocol signals of a remote locomotive controllerconnected to the interface device.
 25. The system of claim 19, whereinthe system controller assembles train and locomotive brake signalsreceived from the interface device and transmits to the electronic airbrake controllers on the network, and assembles and transmits statussignals to the interface device.
 26. The system of claim 19, wherein theinterface device determines the type of remote locomotive controllerconnected to the interface device and assembles EAB network signals forcommunication between the remote locomotive controller and theelectronic air brake controllers on the network for the determined typeof remote locomotive controller.
 27. The system of claim 19, including aremote locomotive controller connected to the interface device; and theremote locomotive controller receives commands from a remote device andgenerates signals to control at least the train brake pipe and thelocomotive brake pipe.
 28. The system of claim 19, including a remotelocomotive controller connected to the interface device, and the remotelocomotive controller generates commands from on-board devices,including EAB network signals, to control at least the train brake pipeand the locomotive brake pipe.
 29. The system of claim 19, including anelectronic brake valve connected to network and providing brakingsignals.
 30. The system of claim 19, wherein the network is a localoperating network (LON) network and the electronic air brakecontrollers, the interface device and the system controller are nodes inthe network.
 31. The system of claim 19, including additional electronicair brake controllers in the network for controlling one or more of abrake cylinder, an electrical train brake line and distributed power.